| Important |
|---|
|
To avoid potentially erroneous results, you should always perform a power-on reboot of your computer before running the diagnostics. |
The Diagnostics and LANAIDC diskette must be created before you run the following procedure. See Appendix A, CD-ROM Content and Software Packages for instructions.
Use the diagnostics program on the Diagnostics and LANAIDC diskette to test the hardware components of the PC Card. Different operating systems will show resources differently.
The diagnostics program performs a series of tests and displays the results of each one by showing success or failure. An error during any test will end the test in progress and display an error message and error code. See the following tables for a description of error codes and recommended actions.
| Note: | The testing process might run as long as 3 minutes and can be exited at any
time by pressing Enter or by removing the Diagnostics and LANAIDC diskette and
pressing Esc. Pressing Esc will cause the computer to reboot.
Pressing Enter will end the test in progress and allow the user to select
another test option.
|
There are two test options: the wrap test and the on-ring test. The on-ring test will not function on a 4-MB token-ring network.
The wrap test ensures that the adapter and cable hardware are functioning properly. For this test, connect the adapter and cable to the network to perform a wrap test through the hub or concentrator, or insert a wrap plug (no wrap plug is required if you have an STP cable connection) to help isolate a failure to the adapter, the cable, or the wiring to the hub or concentrator.
Failure during adapter initialization usually indicates a hardware error on the PC card. Reboot your computer using the diagnostics on the Diagnostics and LANAIDC diskette, and run the diagnostic program again. If the PC card continues to fail, replace it and the cable.
One of the following codes will be shown to indicate the results of the initialization test. The error codes are displayed in hexadecimal format and represent the BRING_UP_CODE set by the adapter.
Failure during the adapter open test might indicate that the adapter is not properly configured to run on the network it is trying to open onto or that the adapter is not properly configured for the system. The open test provides a return code and an open error code. If the return code is 07, then see Open Error Codes for a more accurate description of the failure and suggested actions. If the return code is a value other than 00 or 07, problem determination of the PC Card and the diagnostics is necessary. Record the error and contact your network administrator.
If the open provides a return code of 7, there will be a corresponding error code. The open errors are returned in 2 bytes. The high-order byte is always 0 and the low-order byte contains the following information:
| Value | Meaning |
|---|---|
| 1n | Lobe media test |
| 2n | Physical insertion |
| 3n | Address verification |
| 4n | Roll call poll (neighbor notification) |
| 5n | Request parameters |
| Value | Meaning |
|---|---|
| n1 | Function failure |
| n2 | Signal loss |
| n3 | Reserved |
| n4 | Frequency error (see note) |
| n5 | Time-out |
| n6 | Ring failure |
| n7 | Ring beaconing |
| n8 | Duplicate node address |
| n9 | Parameter request--retry count exceeded |
| nA | Remove received |
| nB | IMPL force received |
| nC | Duplicate modifier |
| nD | No monitor detected |
| nE | Monitor contention failed for RPL |
When the following phase-error combination values are presented, they
are the result of certain specific occurrences. Explanation of the
occurrences follows with recommended actions listed. Table 8 lists the recommended actions for both the application
program and the computer operator.
| Error Code | Explanation | Action |
|---|---|---|
| 11 | Lobe Media, Function Failure: The testing of the lobe between the PC Card and the access unit has been unsuccessful because the lobe has a bit-error rate that is too high, or the PC Card cannot receive successfully. | 1, 3, and 5 |
| 24 | Physical Insertion, Frequency Error: The PC Card has detected that the ring is operating at a speed other than the speed at which it was inserting. | 2 |
| 26 | Physical Insertion, Ring Failure: The PC Card, acting as an active monitor, was unable to complete the ring purge function successfully. This indicates that an error condition has occurred since the successful completion of monitor contention (claim token), when this PC Card became the active monitor. | 1 and 2a |
| 27 | Physical Insertion, Ring Beaconing: The PC Card has detected one of
the following conditions:
| 1, 2, and 2b |
| 2A | Physical Insertion, Remove Received: The PC Card has received a remove ring station MAC frame, indicating that a network management function has directed this PC Card to get off the ring. | 2a and 4 |
| 2D | Physical Insertion, No Monitor Detected: RPL station is the first station attempting to insert onto the ring. | 1 and 2a |
| 2E | Physical Insertion, Monitor Contention Failed for RPL: Physical insertion failure of RPL station. | 2 |
| 32 | Address Verification, Signal Loss: The PC Card has detected a 250-ms signal loss (receiver cannot recognize signal), indicating that an error condition has occurred since the PC Card successfully completed the ring signal recognition phase of the open operation. | 1 and 2a |
| 35 | Address Verification, Time-out: The insertion timer expired before this function was completed, indicating that the ring can be congested, experiencing a high bit-error rate, or losing an abnormally high number of tokens or frames, thus preventing successful Address Verification MAC frame transmissions. | 1 and 2a |
| 36 | Address Verification, Ring Failure: The PC Card, acting as an active monitor, was unable to complete the ring purge function successfully. This indicates that an error condition has occurred since the successful completion of monitor contention (claim token), when this PC Card became the active monitor. | 1 and 2a |
| 37 | Address Verification, Ring Beaconing: The PC Card has either detected a monitor contention (claim token) failure or received a beacon MAC frame from the ring. | 1 and 2b |
| 38 | Address Verification, Duplicate Node Address: The PC Card has detected that another station on the ring has a PC Card address that is the same as the PC card address being tested. | 4 |
| 3A | Address Verification, Remove Received: The PC Card has received a remove ring station MAC frame, indicating that a network management function has directed this specific address to get off the ring. | 2a and 4 |
| 42 | Ring Poll, Signal Loss: The PC Card has detected a 250-ms signal loss (receiver cannot recognize signal) indicating that an error condition has occurred since the PC Card successfully completed the ring signal recognition phase of the open operation. | 1 and 2a |
| 45 | Ring Poll, Time-out: The insertion timer expired before this function was completed, indicating that the ring can be congested, experiencing a high bit-error rate, or losing an abnormally high number of tokens or frames. This prevents the PC Card's successful reception of either the ring poll request or response MAC frame, or transmission of the required ring poll response MAC frame. | 1 and 2a |
| 46 | Ring Poll, Ring Failure: The PC Card, acting as an active monitor, was unable to complete the ring purge function successfully. This indicates that an error condition has occurred since the successful completion of monitor contention (claim token), when this PC Card became the active monitor. | 1 and 2a |
| 47 | Ring Poll, Ring Beaconing: The PC Card has either detected a monitor contention (claim token) failure or received a beacon MAC frame from the ring. | 1 and 2b |
| 4A | Ring Poll, Remove Received: The PC Card has received a remove ring station MAC frame, indicating that a network management function has directed this PC Card to get off the ring. | 2a and 4 |
| 55 | Request Parameters, Time-out: The insertion timer expired before this function was completed, indicating that the ring can be congested, experiencing a high bit-error rate, or losing an abnormally high number of tokens or frames. This prevents successful transmission of the request parameter MAC frame or reception of either the set parameter 1 or set parameter 2 MAC frame (required response to the PC Card's request). | 1 and 2a |
| 56 | Request Parameters, Ring Failure: The PC Card, acting as an active monitor, was unable to complete the ring purge function successfully. This indicates that an error condition has occurred since the successful completion of monitor contention (when this PC Card became the active monitor). | 1 and 2a |
| 57 | Request Parameters, Ring Beaconing: The PC Card has received a beacon MAC frame from the ring. | 1 and 2b |
| 59 | Request Parameters, Parameter Request - Retry Count Exceeded: The PC Card has detected that the ring parameter server is present on the ring but that the required response (set parameter 1 or set parameter 2 MAC frame) was not received in the allotted time. This indicates that the ring can be congested, experiencing a high bit-error rate, or losing an abnormally high number of tokens or frames. | 1 and 2a |
| 5A | Request Parameters, Remove Received: The PC Card has received a remove ring station MAC frame, indicating that a network management function has directed this PC Card to get off the ring. | 2a and 4 |
| Number | Description |
|---|---|
| 1 | After delaying at least 30 seconds, retry the open two times, inserting the same delay between each try. |
| 2 | After delaying at least 30 seconds, check the PC Card configuration (especially the PC Card data rate) and retry the open. |
| 2a | If this error persists, contact your network administrator for assistance and provide Open Error information. |
| 2b | If this error persists, contact your network administrator for assistance. |
| 3 | Contact your network administrator for assistance and provide Open Error information. |
| 4 | Contact your network administrator for assistance and provide Node Address information, and try attaching to the ring after 6 minutes. |
| 5 | If this error persists, problem determination of the PC Card or lobe is necessary. Contact your network administrator for problem determination assistance. |
If you experience time-out errors during the on-ring test, try running the wrap test in the diagnostics. If the wrap test is completed successfully, but the on-ring test fails, it might indicate problems on the Token-Ring network that the adapter is opening onto during the on-ring test.
For any other errors, ensure that the adapter and cabling are properly connected, and retry the test. If the adapter continues to fail, record the error and contact your network administrator.